Method and Apparatus for Using Indication Information of Time Domain Resource Allocation

ABSTRACT

Various embodiments of the present disclosure provide a method for using indication information of time domain resource allocation. The method comprises receiving from a network node indication information of time domain resource allocation for a first type of message. The method further comprises determining a location of time domain resource for a first type of message based at least in part on the indication information and/or configuration information.

FIELD OF THE INVENTION

The present disclosure generally relates to communication networks, andmore specifically, to usage on control information in a communicationnetwork.

BACKGROUND

This section introduces aspects that may facilitate a betterunderstanding of the disclosure. Accordingly, the statements of thissection are to be read in this light and are not to be understood asadmissions about what is in the prior art or what is not in the priorart.

With the rapid development of networking and communication technologies,a terminal device may be connected to different wireless communicationnetworks, such as a long term evolution (LTE)/fourth generation (4G)network or a new radio (NR)/fifth generation (5G) network, to obtainmultiple types of services. In order to connect to a network, a terminaldevice may need to acquire network synchronization and obtain essentialsystem information (SI). For example, the terminal device can get SI ina master information block (MIB) and remaining minimum systeminformation (RMSI). Synchronization signals may be used for adjustingthe operating frequency of the terminal device relative to the network,and for finding proper timing of the received signal from the network.The radio resource and transmission configurations of the SI andsynchronization signals may be informed to the terminal device bycontrol information from the network. In addition, non-RMSI messagessuch as a paging message, a random access response (RAR) message, Msg4of random access procedure and other system information (OSI) may alsobe informed to the terminal device by control information from thenetwork.

SUMMARY

This summary is provided to introduce a selection of concepts in asimplified form that are further described below in the detaileddescription. This summary is not intended to identify key features oressential features of the claimed subject matter, nor is it intended tobe used to limit the scope of the claimed subject matter.

According to a first aspect of the present disclosure, there is provideda method implemented at a terminal device. The method comprisesreceiving from a network node indication information of time domainresource allocation for a first type of message. The method furthercomprises determining a location of time domain resource for a firsttype of message based at least in part on the indication informationand/or configuration information.

According to a second aspect of the present disclosure, there isprovided an apparatus implemented in a terminal device. The apparatuscomprises one or more processors and one or more memories comprisingcomputer program codes. The one or more memories and the computerprogram codes are configured to, with the one or more processors, causethe apparatus at least to perform any step of the method according tothe first aspect of the present disclosure.

According to a third aspect of the present disclosure, there is provideda computer-readable medium having computer program codes embodiedthereon which, when executed on a computer, cause the computer toperform any step of the method according to the first aspect of thepresent disclosure.

According to a fourth aspect of the present disclosure, there isprovided an apparatus implemented in a terminal device. The apparatuscomprises a receiving unit and a determining unit. In accordance withsome exemplary embodiments, the receiving unit is operable to carry outat least the receiving step of the method according to the first aspectof the present disclosure. The determining unit is operable to carry outat least the determining step of the method according to the firstaspect of the present disclosure.

According to a fifth aspect of the present disclosure, there is provideda method implemented at a network node. The method comprises determiningindication information of time domain resource allocation for a firsttype of message. The method further comprises transmitting theindication information to the terminal device. According to someexemplary embodiments, a location of time domain resource for the firsttype of message is determined based at least in part on the indicationinformation and/or configuration information.

According to a sixth aspect of the present disclosure, there is providedan apparatus implemented in a network node. The apparatus comprises oneor more processors and one or more memories comprising computer programcodes. The one or more memories and the computer program codes areconfigured to, with the one or more processors, cause the apparatus atleast to perform any step of the method according to the fifth aspect ofthe present disclosure.

According to a seventh aspect of the present disclosure, there isprovided a computer-readable medium having computer program codesembodied thereon which, when executed on a computer, cause the computerto perform any step of the method according to the fifth aspect of thepresent disclosure.

According to an eighth aspect of the present disclosure, there isprovided an apparatus implemented in a network node. The apparatuscomprises a determining unit and a transmitting unit. In accordance withsome exemplary embodiments, the determining unit is operable to carryout at least the determining step of the method according to the fifthaspect of the present disclosure. The transmitting unit is operable tocarry out at least the transmitting step of the method according to thefifth aspect of the present disclosure.

In accordance with an exemplary embodiment, the indication informationis from a time domain resource allocation table specified for a secondtype of message, and the time domain resource allocation table isunchanged, or added one or more entries specified for the first type ofmessage, or added one or more entries specified for the first type ofmessage and deleted or updated one or more entries specified for thesecond type of message.

In accordance with an exemplary embodiment, the indication informationis from a time domain resource allocation table specified for a firsttype of message.

In accordance with an exemplary embodiment, the time domain resourceallocation table comprises at least one of the following parameters:physical downlink shared channel, PDSCH, mapping type, slot leveloffset, start symbol index and an allocated number of orthogonalfrequency division multiplexing, OFDM, symbols, wherein the PDSCHmapping type comprises Type A and/or Type B, and/or the slot leveloffset comprises 0, 1 and/or integer greater than 1, and/or the startsymbol index comprises at least one of the 0, 1, 2, 3, 4, 6, 8, 9, 10,11, 12, and/or the allocated number of OFDM symbol comprises at leastone of 2, 4, 7, and integer greater than 7.

In accordance with an exemplary embodiment, the configurationinformation is predefined or received from the network node.

In accordance with an exemplary embodiment, the configurationinformation comprises a fixed and/or configurable and/orother-information-dependent offset.

In accordance with an exemplary embodiment, the fixed and/orconfigurable and/or other-information-dependent offset comprisesorthogonal frequency division multiplexing, OFDM, symbol offset and/orslot offset and/or a time offset in other time unit.

In accordance with an exemplary embodiment, if the determined locationof time domain resource by using the fixed and/or configurable and/orother-information-dependent offset is at least partially occupied,adding the fixed and/or configurable and/or other-information-dependentoffset with a predefined value and determining the location of timedomain resource for the first type of message based at least in part onthe indication information and the added fixed and/or configurableand/or other-information-dependent offset.

In accordance with an exemplary embodiment, the configurationinformation is received in at least one of a high layer signaling, thedownlink control information, a broadcast channel, and systeminformation.

In accordance with an exemplary embodiment, the indication informationis received as a part of downlink control information carried by achannel in a control resource set.

In accordance with an exemplary embodiment, the first type of messagecomprises at least one of a paging message, random access response, RAR,message, Msg4 of random access procedure, and other system information,OSI, and a unicast message, and the second type of message comprises aremaining minimum system information, RMSI, message.

According to a ninth aspect of the present disclosure, there is provideda method implemented in a communication system which may include a hostcomputer, a base station and a UE. The method may comprise providinguser data at the host computer. Optionally, the method may comprise, atthe host computer, initiating a transmission carrying the user data tothe UE via a cellular network comprising the base station which mayperform any step of the method according to the fifth aspect of thepresent disclosure.

According to a tenth aspect of the present disclosure, there is provideda communication system including a host computer. The host computer maycomprise processing circuitry configured to provide user data, and acommunication interface configured to forward the user data to acellular network for transmission to a UE. The cellular network maycomprise a base station having a radio interface and processingcircuitry. The base station's processing circuitry may be configured toperform any step of the method according to the fifth aspect of thepresent disclosure.

According to an eleventh aspect of the present disclosure, there isprovided a method implemented in a communication system which mayinclude a host computer, a base station and a UE. The method maycomprise providing user data at the host computer. Optionally, themethod may comprise, at the host computer, initiating a transmissioncarrying the user data to the UE via a cellular network comprising thebase station. The UE may perform any step of the method according to thefirst aspect of the present disclosure.

According to a twelfth aspect of the present disclosure, there isprovided a communication system including a host computer. The hostcomputer may comprise processing circuitry configured to provide userdata, and a communication interface configured to forward user data to acellular network for transmission to a UE. The UE may comprise a radiointerface and processing circuitry. The UE's processing circuitry may beconfigured to perform any step of the method according to the firstaspect of the present disclosure.

According to a thirteenth aspect of the present disclosure, there isprovided a method implemented in a communication system which mayinclude a host computer, a base station and a UE. The method maycomprise, at the host computer, receiving user data transmitted to thebase station from the UE which may perform any step of the methodaccording to the first aspect of the present disclosure.

According to a fourteenth aspect of the present disclosure, there isprovided a communication system including a host computer. The hostcomputer may comprise a communication interface configured to receiveuser data originating from a transmission from a UE to a base station.The UE may comprise a radio interface and processing circuitry. The UE'sprocessing circuitry may be configured to perform any step of the methodaccording to the first aspect of the present disclosure.

According to a fifteenth aspect of the present disclosure, there isprovided a method implemented in a communication system which mayinclude a host computer, a base station and a UE. The method maycomprise, at the host computer, receiving, from the base station, userdata originating from a transmission which the base station has receivedfrom the UE. The base station may perform any step of the methodaccording to the fifth aspect of the present disclosure.

According to a sixteenth aspect of the present disclosure, there isprovided a communication system which may include a host computer. Thehost computer may comprise a communication interface configured toreceive user data originating from a transmission from a UE to a basestation. The base station may comprise a radio interface and processingcircuitry. The base station's processing circuitry may be configured toperform any step of the method according to the fifth aspect of thepresent disclosure.

According to a seventeenth aspect of the present disclosure, there isprovided a method implemented at a terminal device. The method comprisesreceiving from a network node indication information of time domainresource allocation for a non-remaining minimum system information,non-RMSI, message; and determining a location of time domain resourcefor the non-RMSI message based at least in part on the indicationinformation. The indication information is from a physical downlinkshared channel, PDSCH, time domain resource allocation table specifiedfor a remaining minimum system information, RMSI, message. The PDSCHtime domain resource allocation table is associated with synchronizationsignal/physical broadcast channel, SS/PBCH, block and control resourceset, CORESET, multiplexing types 2 and 3, and the indication informationis received as a part of downlink control information carried by achannel in a control resource set.

In an embodiment, the PDSCH time domain resource allocation table may beadded one or more entries.

In an embodiment, the PDSCH time domain resource allocation tablecomprises at least one of the following parameters: physical downlinkshared channel, PDSCH, mapping type, slot level offset, start symbolindex and an allocated number of orthogonal frequency divisionmultiplexing, OFDM, symbols, wherein the PDSCH mapping type comprisesType A and/or Type B, and/or the slot level offset comprises 0, 1 and/orinteger greater than 1, and/or the start symbol index comprises at leastone of the 0, 1, 2, 3, 4, 6, 8, 9, 10, 11, 12, and/or the allocatednumber of OFDM symbol comprises at least one of 2, 4, 7, and integergreater than 7.

In an embodiment, the non-RMSI message comprises at least one of apaging message, random access response, RAR, message, Msg4 of randomaccess procedure, and other system information. OSI, and a unicastmessage.

According to an eighteenth aspect of the present disclosure, there isprovided an apparatus implemented in a terminal device. The apparatuscomprises one or more processors; and one or more memories comprisingcomputer program codes, the one or more memories and the computerprogram codes configured to, with the one or more processors, cause theapparatus at least to receive from a network node indication informationof time domain resource allocation for a non-remaining minimum systeminformation, non-RMSI, message; and determine a location of time domainresource for the non-RMSI message based at least in part on theindication information. The indication information is from a physicaldownlink shared channel, PDSCH, time domain resource allocation tablespecified for a remaining minimum system information, RMSI, message. ThePDSCH time domain resource allocation table is associated withsynchronization signal/physical broadcast channel, SS/PBCH, block andcontrol resource set, CORESET, multiplexing types 2 and 3, and theindication information is received as a part of downlink controlinformation carried by a channel in a control resource set.

According to a nineteenth of the present disclosure, there is provided amethod implemented at a network node. The method comprises determiningindication information of time domain resource allocation for anon-remaining minimum system information, non-RMSI, message; andtransmitting the indication information to the terminal device. Alocation of time domain resource for the non-RMSI message is determinedbased at least in part on the indication information. The indicationinformation is from a physical downlink shared channel, PDSCH, timedomain resource allocation table specified for a remaining minimumsystem information, RMSI, message. The PDSCH time domain resourceallocation table is associated with synchronization signal/physicalbroadcast channel, SS/PBCH, block and control resource set, CORESET,multiplexing types 2 and 3, and the indication information istransmitted as a part of downlink control information carried by achannel in a control resource set.

In an embodiment, the PDSCH time domain resource allocation table isadded one or more entries.

In an embodiment, the PDSCH time domain resource allocation tablecomprises at least one of the following parameters: physical downlinkshared channel, PDSCH, mapping type, slot level offset, start symbolindex and an allocated number of orthogonal frequency divisionmultiplexing, OFDM, symbols, wherein the PDSCH mapping type comprisesType A and/or Type B, and/or the slot level offset comprises 0, 1 and/orinteger greater than 1, and/or the start symbol index comprises at leastone of the 0, 1, 2, 3, 4, 6, 8, 9, 10, 11, 12, and/or the allocatednumber of OFDM symbol comprises at least one of 2, 4, 7, and integergreater than 7.

In an embodiment, the non-RMSI message comprises at least one of apaging message, random access response, RAR, message, Msg4 of randomaccess procedure, and other system information, OSI, and a unicastmessage.

According to a twentieth aspect of the present disclosure, there isprovided an apparatus implemented in a network node. The apparatuscomprises one or more processors; and one or more memories comprisingcomputer program codes, the one or more memories and the computerprogram codes configured to, with the one or more processors, cause theapparatus at least to determine indication information of time domainresource allocation for a non-remaining minimum system information,non-RMSI, message; and transmit the indication information to theterminal device. A location of time domain resource for the non-RMSImessage is determined based at least in part on the indicationinformation. The indication information is from a physical downlinkshared channel, PDSCH, time domain resource allocation table specifiedfor a remaining minimum system information, RMSI, message. The PDSCHtime domain resource allocation table is associated with synchronizationsignal/physical broadcast channel, SS/PBCH, block and control resourceset, CORESET, multiplexing types 2 and 3, and the indication informationis transmitted as a part of downlink control information carried by achannel in a control resource set.

According to a twenty-first aspect of the present disclosure, there isprovided a computer-readable medium having computer program codesembodied thereon for use with a computer, wherein the computer programcodes comprise codes for performing the method according to theseventeenth aspect of the present disclosure.

According to a twenty-second aspect of the present disclosure, there isprovided a computer-readable medium having computer program codesembodied thereon for use with a computer, wherein the computer programcodes comprise codes for performing the method according to thenineteenth aspect of the present disclosure.

According to a twenty-third aspect of the present disclosure, there isprovided an apparatus implemented in a terminal device. The apparatuscomprises a receiving unit configured to receive from a network nodeindication information of time domain resource allocation for anon-remaining minimum system information, non-RMSI, message; and adetermining unit configured to determine a location of time domainresource for the non-RMSI message based at least in part on theindication information. The indication information is from a physicaldownlink shared channel, PDSCH, time domain resource allocation tablespecified for a remaining minimum system information, RMSI, message. ThePDSCH time domain resource allocation table is associated withsynchronization signal/physical broadcast channel, SS/PBCH, block andcontrol resource set, CORESET, multiplexing types 2 and 3, and theindication information is received as a part of downlink controlinformation carried by a channel in a control resource set.

According to a twenty-fourth aspect of the present disclosure, there isprovided an apparatus implemented in a network node. The apparatuscomprises a determining unit configured to determine indicationinformation of time domain resource allocation for a non-remainingminimum system information, non-RMSI, message; and a transmitting unitconfigured to transmit the indication information to the terminaldevice. A location of time domain resource for the non-RMSI message isdetermined based at least in part on the indication information. Theindication information is from a physical downlink shared channel,PDSCH, time domain resource allocation table specified for a remainingminimum system information, RMSI, message. The PDSCH time domainresource allocation table is associated with synchronizationsignal/physical broadcast channel, SS/PBCH, block and control resourceset, CORESET, multiplexing types 2 and 3, and the indication informationis transmitted as a part of downlink control information carried by achannel in a control resource set.

The proposed solution according to one or more exemplary embodiments canenable a network node (such as a gNB) and a terminal device (such as aUE) to determine a location of time domain resource for a specific typeof message based at least in part on the indication information and/orthe configuration information. By applying the proposed solutionaccording to the present disclosure, a more flexible time domainresource allocation can be realized.

BRIEF DESCRIPTION OF THE DRAWINGS

The disclosure itself, the preferable mode of use and further objectivesare best understood by reference to the following detailed descriptionof the embodiments when read in conjunction with the accompanyingdrawings, in which:

FIG. 1 is a diagram illustrating exemplary SSB mapping according to someembodiments of the present disclosure;

FIG. 2 is a diagram illustrating exemplary multiplexing types for SSBand RMSI CORESET according to some embodiments of the presentdisclosure;

FIG. 3 is a flowchart illustrating a method according to someembodiments of the present disclosure;

FIG. 4 is a diagram illustrating an example of using the fixed offsetaccording to some embodiments of the present disclosure;

FIG. 5 is a flowchart illustrating another method according to someembodiments of the present disclosure;

FIG. 6 is a block diagram illustrating an apparatus according to someembodiments of the present disclosure;

FIG. 7 is a block diagram illustrating another apparatus according tosome embodiments of the present disclosure;

FIG. 8 is a block diagram illustrating yet another apparatus accordingto some embodiments of the present disclosure;

FIG. 9 is a block diagram illustrating a telecommunication networkconnected via an intermediate network to a host computer in accordancewith some embodiments of the present disclosure;

FIG. 10 is a block diagram illustrating a host computer communicatingvia a base station with a UE over a partially wireless connection inaccordance with some embodiments of the present disclosure;

FIG. 11 is a flowchart illustrating a method implemented in acommunication system, in accordance with an embodiment of the presentdisclosure;

FIG. 12 is a flowchart illustrating a method implemented in acommunication system, in accordance with an embodiment of the presentdisclosure;

FIG. 13 is a flowchart illustrating a method implemented in acommunication system, in accordance with an embodiment of the presentdisclosure; and

FIG. 14 is a flowchart illustrating a method implemented in acommunication system, in accordance with an embodiment of the presentdisclosure.

DETAILED DESCRIPTION

The embodiments of the present disclosure are described in detail withreference to the accompanying drawings. It should be understood thatthese embodiments are discussed only for the purpose of enabling thoseskilled persons in the art to better understand and thus implement thepresent disclosure, rather than suggesting any limitations on the scopeof the present disclosure. Reference throughout this specification tofeatures, advantages, or similar language does not imply that all of thefeatures and advantages that may be realized with the present disclosureshould be or are in any single embodiment of the disclosure. Rather,language referring to the features and advantages is understood to meanthat a specific feature, advantage, or characteristic described inconnection with an embodiment is included in at least one embodiment ofthe present disclosure. Furthermore, the described features, advantages,and characteristics of the disclosure may be combined in any suitablemanner in one or more embodiments. One skilled in the relevant art willrecognize that the disclosure may be practiced without one or more ofthe specific features or advantages of a particular embodiment. In otherinstances, additional features and advantages may be recognized incertain embodiments that may not be present in all embodiments of thedisclosure.

As used herein, the term “communication network” refers to a networkfollowing any suitable communication standards, such as new radio (NR),long term evolution (LTE), LTE-Advanced, wideband code division multipleaccess (WCDMA), high-speed packet access (HSPA), and so on. Furthermore,the communications between a terminal device and a network node in thecommunication network may be performed according to any suitablegeneration communication protocols, including, but not limited to, thefirst generation (1G), the second generation (2G), 2.5G, 2.75G, thethird generation (3G), 4G, 4.5G, 5G communication protocols, and/or anyother protocols either currently known or to be developed in the future.

The term “network node” refers to a network device in a communicationnetwork via which a terminal device accesses to the network and receivesservices therefrom. The network node may refer to a base station (BS),an access point (AP), a multi-cell/multicast coordination entity (MCE),a controller or any other suitable device in a wireless communicationnetwork. The BS may be, for example, a node B (NodeB or NB), an evolvedNodeB (eNodeB or eNB), a next generation NodeB (gNodeB or gNB), a remoteradio unit (RRU), a radio header (RH), a remote radio head (RRH), arelay, a low power node such as a femto, a pico, and so forth.

Yet further examples of the network node comprise multi-standard radio(MSR) radio equipment such as MSR BSs, network controllers such as radionetwork controllers (RNCs) or base station controllers (BSCs), basetransceiver stations (BTSs), transmission points, transmission nodes,positioning nodes and/or the like. More generally, however, the networknode may represent any suitable device (or group of devices) capable,configured, arranged, and/or operable to enable and/or provide aterminal device access to a wireless communication network or to providesome service to a terminal device that has accessed to the wirelesscommunication network.

The term “terminal device” refers to any end device that can access acommunication network and receive services therefrom. By way of exampleand not limitation, the terminal device may refer to a mobile terminal,a user equipment (UE), or other suitable devices. The UE may be, forexample, a subscriber station, a portable subscriber station, a mobilestation (MS) or an access terminal (AT). The terminal device mayinclude, but not limited to, portable computers, image capture terminaldevices such as digital cameras, gaming terminal devices, music storageand playback appliances, a mobile phone, a cellular phone, a smartphone, a tablet, a wearable device, a personal digital assistant (PDA),a vehicle, and the like.

As yet another specific example, in an Internet of things (IoT)scenario, a terminal device may also be called an IoT device andrepresent a machine or other device that performs monitoring, sensingand/or measurements etc., and transmits the results of such monitoring,sensing and/or measurements etc. to another terminal device and/or anetwork equipment. The terminal device may in this case be amachine-to-machine (M2M) device, which may in a 3rd generationpartnership project (3GPP) context be referred to as a machine-typecommunication (MTC) device.

As one particular example, the terminal device may be a UE implementingthe 3GPP narrow band Internet of things (NB-IoT) standard. Particularexamples of such machines or devices are sensors, metering devices suchas power meters, industrial machinery, or home or personal appliances,e.g. refrigerators, televisions, personal wearables such as watches etc.In other scenarios, a terminal device may represent a vehicle or otherequipment, for example, a medical instrument that is capable ofmonitoring, sensing and/or reporting etc. on its operational status orother functions associated with its operation.

As used herein, the terms “first”, “second” and so forth refer todifferent elements. The singular forms “a” and “an” are intended toinclude the plural forms as well, unless the context clearly indicatesotherwise. The terms “comprises”, “comprising”, “has”, “having”,“includes” and/or “including” as used herein, specify the presence ofstated features, elements, and/or components and the like, but do notpreclude the presence or addition of one or more other features,elements, components and/or combinations thereof. The term “based on” isto be read as “based at least in part on”. The term “one embodiment” and“an embodiment” are to be read as “at least one embodiment”. The term“another embodiment” is to be read as “at least one other embodiment”.Other definitions, explicit and implicit, may be included below.

Wireless communication networks are widely deployed to provide varioustelecommunication services such as voice, video, data, messaging andbroadcasts. As described previously, in order to connect to a wirelesscommunication network, a terminal device may need to acquire networksynchronization and obtain essential ST such as RMSI. In a wirelesscommunication network such as NR, the synchronization and accessprocedure may involve several signals, for example, a primarysynchronization signal (PSS) and a secondary synchronization signal(SSS).

The PSS may allow for network detection in the presence of a highinitial frequency error, for example, up to tens of ppm. The SSS mayallow for more accurate frequency adjustments and channel estimationwhile providing fundamental network information, such as a cellidentifier (ID).

A physical broadcast channel (PBCH) may provide a subset of the minimumsystem information for random access and configurations for fetchingremaining minimum system information in RMSI. It also may provide timinginformation within a cell, for example, to separate timing between beamstransmitted from a cell. The amount of information to fit into the PBCHis of course highly limited to keep the size down. Furthermore,demodulation reference signals (DMRS) may be interleaved with PBCHresources in order to receive the PBCH properly.

A SS/PBCH block or SSB may comprise the above signals (such as PSS, SSSand DMRS) and PBCH. For example, the SSB may have 15 kHz, 30 kHz, 120kHz or 240 kHz subcarrier spacing (SCS) depending on the frequencyrange.

FIG. 1 is a diagram illustrating exemplary SSB mapping according to someembodiments of the present disclosure. In FIG. 1, each numbered smallbox represents an orthogonal frequency division multiplexing (OFDM)symbol, and dark symbols represent the mapping of candidate SSBpositions at which SSB may be transmitted. As illustrated in FIG. 1, onecandidate SSB position may correspond to four OFDM symbols. FIG. 1Ashows some exemplary candidate SSB positions within two slots for thecases of 15 kHz SCS, 30 kHz SCS (including pattern 1 and pattern 2) and120 kHz SCS, and within four slots for the case of 240 kHz SCS.

According to an exemplary embodiment, a SS burst set may be transmittedperiodically with the periodicity configured in RMSI. For example, 20 msSS burst set periodicity may be assumed for initial access. By using theSSBs in the SS burst set, a UE can determine the downlink timing,frequency offset and/or the like, and acquire some fundamental systeminformation from the PBCH. When the UE obtained downlinksynchronization, it may know in which slots to expect SSB transmissions.Thus, the location of the SSB in a SS burst set may need to be providedto the UE to derive the subframe level synchronization.

In addition to network synchronization, some SI such as RMSI may also beimportant for a UE to connect to a network. RMSI may be carried in aphysical downlink shared channel (PDSCH) scheduled by a physicaldownlink control channel (PDCCH) in the CORESET configured by a PBCH inNR. RMSI may contain the remaining subset of minimum system information,for example, the bitmap to indicate the actually transmitted SSBs.

The CORESET configured by the PBCH can also be used for other systeminformation (OSI), paging, random access respond (RAR), and/or the like.In accordance with exemplary embodiments, the CORESET configured by thePBCH may consist of a number (denoted as N_(RB) ^(CORESET)) of resourceblocks in the frequency domain, and a number (denoted as N_(symb)^(CORESET)) of OFDM symbols in the time domain. For example, N_(RB)^(CORESET) an may be 24, 48 or 96, and N_(symb) ^(CORESET) may be 1, 2or 3.

After detecting one SSB, a UE may try to search the possible PDCCHcandidates based at least in part on the CORESET configurations if theyare present in the PBCH. In accordance with exemplary embodiments, theremay be several possible multiplexing types between the SSB and theCORESET configured by PBCH (also known as RMSI CORESET).

FIG. 2 is a diagram illustrating exemplary multiplexing types for SSBand RMSI CORESET according to some embodiments of the presentdisclosure. As illustrated in FIG. 2, three multiplexing types (denotedas type 1, type 2 and type 3) may be applicable to the SSB and the RMSICORESET in time domain and/or frequency domain. Among these multiplexingtypes, type 1 may be supported in sub-6 GHz and/or over-6 GHz frequencybands, while type 2 and type 3 are only supported in over-6 GHzfrequency bands.

In accordance with exemplary embodiments, each multiplexing type mayhave a set of supported numerology combinations {SSB SCS, RMST SCS}. Forexample, a set of numerology combinations {SSB SCS, RMSI SCS} supportedby type 1 in sub-6 GHz frequency bands may comprise {15 kHz, 15 kHz},{15 kHz, 30 kHz}, {30 kHz, 15 kHz} and {30 kHz, 30 kHz}, and a set ofnumerology combinations {SSB SCS, RMSI SCS} supported by type 1 inover-6 GHz frequency bands may comprise {120 kHz, 60 kHz}, {120 kHz, 120kHz}, {240 kHz, 60 kHz} and (240 kHz, 120 kHz). Similarly, a set ofnumerology combinations {SSB SCS, RMSI SCS} supported by type 2 inover-6 GHz frequency bands may comprise {120 kHz, 60 kHz} and {240 kHz,120 kHz}, and a set of numerology combinations {SSB SCS, RMSI SCS}supported by type 3 in over-6 GHz frequency bands may comprise {120 kHz,120 kHz}.

FIG. 2 also shows the relationship between bandwidth of a PDSCH andbandwidth of the CORESET containing the PDCCH scheduling this PDSCH.According to an exemplary embodiment, the initial active downlink (DL)bandwidth part (BWP) may be defined as the frequency location andbandwidth of RMSI CORESET and the numerology of RMSI. The PDSCHdelivering RMSI may be confined within the initial active DL BWP. A UEcan learn specific resource configurations (such as time domain and/orfrequency domain resource allocation) from downlink control information(DCI). The DCI may be used for scheduling RMSI, a paging message, randomaccess response (RAR) message, Msg4 of random access procedure, andother system information (OSI), etc. For example, when the UE isscheduled to receive PDSCH by a DCI, the Time domain resource assignmentfield value m of the DCI provides a row index m+1 to an allocationtable.

In 3GPP meeting RAN1 #92bis, below tables 5.1.2.1.1-1, 5.1.2.1.1-2,5.1.2.1.1-3 and 5.1.2.1.1-4 have been agreed for time domain resourceallocation of PDSCH carrying RMSI in case of type 1, type 2 and type 3respectively. These tables are from a section of 5.1.2.1.13 of 3GPP TS38.214, which is incorporated herein by reference in its entirety.

Table 5.1.2.1.1-1 defines which PDSCH time domain resource allocationconfiguration to apply. Either a default PDSCH time domain allocation A,B or C according to tables 5.1.2.1.1-2, 5.1.2.1.1-3 and 5.1.2.1.1-4respectively is applied, or a high layer configured pdsch-AllocationListin either pdsch-ConfigCommon or pdsch-Config is applied.

TABLE 5.1.2.1.1-1 Applicable PDSCH time domain resource allocationSS/PBCH PDSCH block and pdsch- time domain CORESET ConfigCommonpdsch-Config resource PDCCH multiplexing includes pdsch- includes pdsch-allocation RNT1 search space pattern AllocationList AllocationList toapply SI-RNTI Type0 1 — — Default A common 2 — — Default B 3 — — DefaultC Type0A common RA-RNTI, Type1 TC-RNTI, common C-RNTI P-RNTI Type2common C-RNTI, Type3 CS-RNT1 common C-RNTI, UE specific 1, 2, 3 No NoDefault A CS-RNTI 1, 2, 3 Yes No pdsch- AllocationList provided inpdsch- ConfigCommon 1, 2, 3 No/Yes Yes pdsch- Allocation List providedin pdsch-Config

TABLE 5.1.2.1.1-2 Default PDSCH time domain resource allocation A dmrs-PDSCH Row TypeA- mapping index Position type K₀ S L 1 2 Type A 0 2 12 3Type A 0 3 11 2 2 Type A 0 2 10 3 Type A 0 3 9 3 2 Type A 0 2 9 3 Type A0 3 8 4 2 Type A 0 2 1 3 Type A 0 3 6 5 2 Type A 0 2 5 3 Type A 0 3 4 62 Type B 0 9 4 3 Type B 0 10 4 7 2 Type B 0 4 4 3 Type B 0 6 4 8 2, 3Type B 0 5 7 9 2, 3 Type B 0 5 2 10 2, 3 Type B 0 9 2 11 2, 3 Type B 012 2 12 2, 3 Type A 0 1 13 13 2, 3 Type A 0 1 6 14 2, 3 Type A 0 2 4 152, 3 Type B 0 4 7 16 2, 3 Type B 0 8 4

TABLE 5.1.2.1.1-3 Default PDSCH time domain resource allocation B PDSCHRow mapping index type K₀ S L 1 Type B 0 2 2 2 Type B 0 4 2 3 Type B 0 62 4 Type B 0 8 2 5 Type B 0 10 2 6 Type B 1 2 2 7 Type B 1 4 2

TABLE 5.1.2.1.1-4 Default PDSCH time domain resource allocation C PDSCHRow mapping index type K₀ S L 1 Type B 0 4 2 2 Type B 0 6 2 3 Type B 0 82 4 Type B 0 10 2

Note that from a table size perspective, for default PDSCH time domainresource allocation B, it is possible to add 7 more rows with same K₀and S as above but with L=4 as well as 2 more rows S=0 and L=4. Fordefault PDSCH time domain resource allocation C, more entries can beadded.

4 bits in DCI is used to indicate which time domain resource allocationtable entry is used for the time domain resource allocation for PDSCH.In each entry, the parameter K₀ is the slot level offset from the slotincluding this DCI, the parameter S is the start symbol index (0 to 13)within a slot, and the parameter L is the number of OFDM symbolsallocated.

In case the SSB and RMSI are multiplexed with type 2 and type 3, theagreed tables are only for RMSI scheduling. For non-RMSI messages suchas the paging message, RAR message, Msg4 of random access procedure, OSIetc., some more flexible scheduling methods may be required when they'rescheduled in CORESET configured by PBCH.

In the proposed solution according to some exemplary embodiments, anetwork node can provide a terminal device with indication informationof time domain resource allocation for the non-RMSI message. In anembodiment, the above Table 5.1.2.1.1-2, 5.1.2.1.1-3 and 5.1.2.1.1-4 maybe reused via introducing one or more entries and/or deleting one ormore entries that is not often used to meet the maximum 16 entryrequirement. In another embodiment, the above Table 5.1.2.1.1-2,5.1.2.1.1-3 and 5.1.2.1.1-4 may be reused via introducing someadditional fixed OFDM symbol level offset. In another embodiment, theabove Table 5.1.2.1.1-2, 5.1.2.1.1-3 and 5.1.2.1.1-4 may be reused viaintroducing some additional configurable OFDM symbol level offset. Theconfigurable OFDM symbol level offset can be signaled, e.g. in RMSI orPBCH. In another embodiment, the above Table 5.1.2.1.1-2, 5.1.2.1.1-3and 5.1.2.1.1-4 may be reused and combined with other networkconfiguration parameters provided either via a high layer signaling orDCI field to decide the PDSCH allocation. In another embodiment, a newtable for non-RMSI PDSCHs may be defined. The new table may allow moreflexible time domain OFDM symbol positions that are not limited with inthe time duration of SSB and allow more slot level offset between PDCCHand PDSCH than the current table.

It is noted that some embodiments of the present disclosure are mainlydescribed in relation to 5G or NR specifications being used asnon-limiting examples for certain exemplary network configurations andsystem deployments. As such, the description of exemplary embodimentsgiven herein specifically refers to terminology which is directlyrelated thereto. Such terminology is only used in the context of thepresented non-limiting examples and embodiments, and does naturally notlimit the present disclosure in any way. Rather, any other systemconfiguration or radio technologies may equally be utilized as long asexemplary embodiments described herein are applicable.

FIG. 3 is a flowchart illustrating a method 300 according to someembodiments of the present disclosure. The method 300 illustrated inFIG. 3 may be performed by an apparatus implemented in a terminal deviceor communicatively coupled to a terminal device. In accordance with someexemplary embodiments, the terminal device such as a UE can supportvarious multiplexing types between SSB and CORESET, for example,multiplexing type 1, type 2 and type 3 as shown in FIG. 2. The terminaldevice UE can know which time domain resource allocation table iscurrently used, for example, Table 5.1.2.1.1-2, 5.1.2.1.1-3, 5.1.2.1.1-4or any other suitable time domain resource allocation tables. It will beappreciated that some embodiments of the present disclosure also may beapplicable for other use cases, for example, multiplexing types betweenother different signal transmissions.

According to the exemplary method 300 illustrated in FIG. 3, theterminal device may receive from a network node indication informationof time domain resource allocation for a first type of message as shownin block 302 and determine a location of time domain resource for afirst type of message based at least in part on the indicationinformation and/or configuration information, as shown in block 304.

In accordance with an exemplary embodiment, the indication informationmay be received as a part of DCI carried by a channel in a CORESET. TheDCI may comprise DCI carried by a PDCCH in CORESET, or other proper typeof DCI. For example, the DCI may have one or more fields containingvarious parameters, indicators, etc. The indication information maycomprise one or more bits in a time domain resource allocation field ofthe DCI. It will be appreciated that the indication information may alsobe included in the DCI in other suitable forms. For example, theindication information in the time domain resource allocation field mayform a new field of the DCI together with one or more bits in otherfield of the DCI.

In accordance with an exemplary embodiment, the configurationinformation may be predefined or received from the network node. Forexample, if the configuration information is predefined, the terminaldevice and the network device may prestore the configurationinformation. As another example, the network node may send theconfiguration information to the terminal device for example whenconfiguration information is changed or updated. The configurationinformation may comprise any suitable information that can be used bythe terminal device to determine the location of time domain resourcefor the first type of message. For example, the configurationinformation may indicate that the location of time domain resource forthe first type of message is determined based on only the indicationinformation. As another example, the configuration information maycomprise offset information. In this case, the location of time domainresource for the first type of message may be determined based on theindication information and the offset information.

In accordance with an exemplary embodiment, the configurationinformation may comprise a fixed and/or configurable and/orother-information-dependent offset. The offset may refer to the offsetof any suitable parameters indicated in the indication information. Theoffset may be determined by using various approaches, for example, basedon time domain resource allocation of other messages. Theother-information may be any suitable information such as 1) messagetypes, corresponding to different RNTI types used for CRC (CyclicRedundancy Check) scrambling of PDCCH scheduling the PDSCH, e.g. P-RNTI,2) frequency band, 3) maximum number of beams used, 4) the pagingoccasion definition, etc. For example, the paging message that needs alarger slot offset can interpret the indication information with apredefined slot offset. There may be any other suitableother-information-dependent offset in other embodiments.

In accordance with an exemplary embodiment, the fixed and/orconfigurable and/or other-information-dependent offset may comprise OFDMsymbols offset and/or slot offset and/or a time offset in other timeunit. For example, the fixed or configurable offset may indicates that nsymbol offset can be added to a start OFDM symbol indicated by theindication information. The fixed or configurable offset may indicatesthat m slot offset can be added to the slot indicated by the indicationinformation.

In accordance with an exemplary embodiment, if the determined locationof time domain resource by using the fixed and/or configurable and/orother-information-dependent offset is at least partially occupied, thefixed and/or configurable and/or other-information-dependent offset maybe added with a predefined value and the location of time domainresource for the first type of message may be determined based at leastin part on the indication information and the added fixed and/orconfigurable and/or other-information-dependent offset. The predefinedvalue may be any suitable value that may be determined by using anysuitable approaches, for example based on history information of thetime domain resource allocation. It is noted that the above operationcan be performed one or more times until the determined location of timedomain resource is not occupied.

For example, for multiplexing pattern 3, the SSB and RMSI always havesame subcarrier spacing, i.e. 120 kHz, for non-RMSI (such as the firsttype of message) PDSCH scheduling, n symbol offset can be added to thestart symbol number S in Table 5.1.2.1.1-2, 5.1.2.1.1-3 and 5.1.2.1.1-4,and if the scheduled symbol (after the n symbol offset is added to S)overlaps with for example a further RMSI CORESET, the UE could assumethat another n symbol offset to the S should be added to fetch thenon-RMSI PDSCH.

FIG. 4 is a diagram illustrating an example of using the fixed offsetaccording to some embodiments of the present disclosure. As shown inFIG. 4, if one PDSCH is scheduled by DC in symbols 4 and 5 in the firstslot (14 symbols each slot, 2 slots are shown in FIG. 4), and a rowindex is indicated in DCI as 2 in Table 5.1.2.1.1-4, i.e. the startsymbol of PDSCH is 6 and length is 2. Then if it's a non-RMSI message(i.e. the PDCCH carrying the DCI is not scrambled by SI-RNTI), the fixedsymbols offset such as 2 may be added to the S, i.e. S=8, length is 2,but this location may be the CORESET associated with the next SSB, soone additional offset of 2 symbols can be added, i.e. S=10 for non-RMSIscheduling.

In accordance with an exemplary embodiment, the configurationinformation may be received in at least one of a high layer signaling,the downlink control information, a broadcast channel, and systeminformation. The high layer signaling may be layer 2 or above signaling,for example, radio resource control (RRC) signaling. The broadcastchannel may be PBCH or other suitable broadcast channel. The systeminformation may be RMSI or other suitable system information.

In accordance with an exemplary embodiment, the indication informationis from a time domain resource allocation table specified for a secondtype of message and the time domain resource allocation table isunchanged, which may mean that the indication information is determinedby the network node according to the time domain resource allocationtable specified for the second type of message. The first type ofmessage and the second type of message may be different. For example,the first type of message may comprise at least one of a paging message,RAR message, Msg4 of random access procedure, OSI, a unicast message,etc. The second type of message may comprise the RMSI message. Forexample, the time domain resource allocation table may be at least oneof the Table 5.1.2.1.1-2, 5.1.2.1.1-3 and 5.1.2.1.1-4 or any othersuitable table. The indication information may be the “Row index” ofthese tables. In this embodiment, the terminal device may determine thelocation of time domain resource for the first type of message based atleast in part on the indication information and the configurationinformation as described above.

In accordance with an exemplary embodiment, the indication informationis from a time domain resource allocation table specified for the secondtype of message, and the time domain resource allocation table is addedone or more entries specified for the first type of message. Forexample, the Table 5.1.2.1.1-2, 5.1.2.1.1-3 and 5.1.2.1.1-4 may bereused via introducing one or more entries and/or deleting one or morethe entries that is not often used to meet the maximum 16 entryrequirement. As an example, for multiplexing type 2, Table 1 can beobtained based on the allowed OFDM symbol positions for non-RMSI PDSCHand with removal of some entries with odd numbered start symbol S,wherein row indexes 8-16 are added entries for the first type ofmessage.

TABLE 1 PDSCH Row mapping index type K₀ S L 1 Type B 0 2 2 2 Type B 0 42 3 Type B 0 6 2 4 Type B 0 8 2 5 Type B 0 10 2 6 Type B 1 2 2 7 Type B1 4 2 8 Type B 0 2 4 9 Type B 0 8 4 10 Type B 0 4 4 11 Type B 0 6 4 12Type B 0 4 7 13 Type B 0 10 4 14 Type B 0 2 7 15 Type B 0 3 7 16 Type B0 6 7For multiplexing type 3, table 3 can be obtained as below, wherein rowindexes 5-9 are added entries for the first type of message.

TABLE 2 PDSCH Row mapping index type K₀ S L 1 Type B 0 4 2 2 Type B 0 62 3 Type B 0 8 2 4 Type B 0 10 2 5 Type B 0 12 2 6 Type B 1 0 2 7 Type B1 2 2 8 Type B 0 8 4 9 Type B 0 10 4

In accordance with an exemplary embodiment, the indication informationis from a time domain resource allocation table specified for the firsttype of message. In this embodiment, the terminal device may determine alocation of time domain resource for a first type of message based onthe indication information. Alternatively, the terminal device maydetermine a location of time domain resource for a first type of messagebased on the indication information and the configuration information asdescribed above.

In accordance with an exemplary embodiment, the time domain resourceallocation table may comprise at least one of the following parameters:physical downlink shared channel, PDSCH, mapping type, slot leveloffset, start symbol index and an allocated number of orthogonalfrequency division multiplexing, OFDM, symbols, wherein the PDSCHmapping type comprises Type A and/or Type B as shown in the Table5.1.2.1.1-2, 5.1.2.1.1-3 and 5.1.2.1.1-4, and/or the slot level offsetcomprises 0, 1 and/or integer greater than 1, and/or the start symbolindex comprises at least one of the 0, 1, 2, 3, 4, 6, 8, 9, 10, 11, 12,and/or the allocated number of OFDM symbol comprises at least one of 2,4, 7, and integer greater than 7.

For example, a new default table for non-RMSI PDSCHs may not include allthe rows for RMSI scheduling. Assuming CORESET and PDSCH in differentslots are not supported for some non-RMSI PDSCH scheduling(alternatively: not supported for (some) unicast PDSCH scheduling), ontop of which non-RMSI PDSCH reuses the RMSI entries when L=2, then someadditional entries with odd numbered start symbol S may be removed toget Table 3 for non-RMSI PDSCH.

TABLE 3 PDSCH Row mapping index type K₀ S L 1 Type B 0 2 2 2 Type B 0 42 3 Type B 0 6 2 4 Type B 0 8 2 5 Type B 0 10 2 6 Type B 0 2 4 7 Type B0 8 4 8 Type B 0 4 4 9 Type B 0 6 4 10 Type B 0 4 7 11 Type B 0 3 4 12Type B 0 9 4 13 Type B 0 10 4 14 Type B 0 2 7 15 Type B 0 3 7 16 Type B0 6 7

It will be appreciated that Table 1-3 are just shown as examples andvarious alternative parameter settings may be applicable to thecommunication between the terminal device and the network node accordingto the embodiments of the present disclosure.

FIG. 5 is a flowchart illustrating a method 500 according to someembodiments of the present disclosure. The method 500 illustrated inFIG. 5 may be performed by an apparatus implemented in a network node orcommunicatively coupled to a network node. In accordance with anexemplary embodiment, the network node such as a gNB can support variousmultiplexing types between SSB and CORESET, for example, multiplexingtype 1, type 2 and type 3 as shown in FIG. 2. The network node can knowwhich time domain resource allocation table may be selected to used, forexample, Table 5.1.2.1.1-2, 5.1.2.1.1-3, 5.1.2.1.1-4 or any othersuitable time domain resource allocation tables. Then the network nodemay determine indication information of time domain resource allocationfor a specific type of message. It will be appreciated that someembodiments of the present disclosure also may be applicable for otheruse cases, for example, multiplexing types between other differentsignal transmissions. For some parts which have been described in theabove embodiments, detailed description thereof is omitted here forbrevity.

According to the exemplary method 500 illustrated in FIG. 5, the networknode can determine indication information of time domain resourceallocation for a first type of message as shown in block 502 andtransmit the indication information to the terminal device as shown inblock 504. In this embodiment, the location of time domain resource forthe first type of message is determined based at least in part on theindication information and/or configuration information.

In accordance with an exemplary embodiment, the indication informationis from a time domain resource allocation table specified for a secondtype of message, and the time domain resource allocation table isunchanged, or added one or more entries specified for the first type ofmessage, or added one or more entries specified for the first type ofmessage and deleted or updated one or more entries specified for thesecond type of message.

In accordance with an exemplary embodiment, the indication informationis from a time domain resource allocation table specified for a firsttype of message.

In accordance with an exemplary embodiment, the time domain resourceallocation table comprises at least one of the following parameters:physical downlink shared channel, PDSCH, mapping type, slot leveloffset, start symbol index and an allocated number of orthogonalfrequency division multiplexing, OFDM, symbols, wherein the PDSCHmapping type comprises Type A and/or Type B as shown in the Table5.1.2.1.1-2, 5.1.2.1.1-3 and 5.1.2.1.1-4, and/or the slot level offsetcomprises 0, 1 and/or integer greater than 1, and/or the start symbolindex comprises at least one of the 0, 1, 2, 3, 4, 6, 8, 9, 10, 11, 12,and/or the allocated number of OFDM symbol comprises at least one of 2,4, 7, and integer greater than 7.

In accordance with an exemplary embodiment, the configurationinformation is predefined or generated by the network node, and when theconfiguration information is generated by the network node, the methodfurther comprises sending the configuration information to the terminaldevice.

In accordance with an exemplary embodiment, the configurationinformation comprises a fixed and/or configurable and/orother-information-dependent offset.

In accordance with an exemplary embodiment, the fixed and/orconfigurable and/or other-information-dependent offset comprisesorthogonal frequency division multiplexing, OFDM, symbol offset and/orslot offset and/or a time offset in other time unit.

In accordance with an exemplary embodiment, if the determined locationof time domain resource by using the fixed and/or configurable and/orother-information-dependent offset is at least partially occupied, thefixed and/or configurable and/or other-information-dependent offset isadded with a predefined value and the location of time domain resourcefor the first type of message is determined based at least in part onthe indication information and the added fixed and/or configurableand/or other-information-dependent offset.

In accordance with an exemplary embodiment, the configurationinformation is sent in at least one of a high layer signaling, thedownlink control information, a broadcast channel, and systeminformation.

In accordance with an exemplary embodiment, the indication informationis sent as a part of downlink control information carried by a channelin a control resource set.

In accordance with an exemplary embodiment, the first type of messagecomprises at least one of a paging message, random access response, RAR,message, Msg4 of random access procedure, and other system information,OSI, and a unicast message, and the second type of message comprises aremaining minimum system information, RMSI, message.

It will be realized that parameters, variables and settings related tothe time domain resource allocation described herein are just examples.Other suitable network settings, the associated configuration parametersand the specific values thereof may also be applicable to implement theproposed methods.

The proposed solution according to one or more exemplary embodiments canenable a network node (such as a gNB) and a terminal device (such as aUE) to determine a location of time domain resource for a specific typeof message based at least in part on the indication information and/orthe configuration information. By applying the proposed solutionaccording to the present disclosure, a more flexible time domainresource allocation can be realized.

The various blocks shown in FIG. 3 and FIG. 5 may be viewed as methodsteps, and/or as operations that result from operation of computerprogram code, and/or as a plurality of coupled logic circuit elementsconstructed to carry out the associated function(s). The schematic flowchart diagrams described above are generally set forth as logical flowchart diagrams. As such, the depicted order and labeled steps areindicative of specific embodiments of the presented methods. Other stepsand methods may be conceived that are equivalent in function, logic, oreffect to one or more steps, or portions thereof, of the illustratedmethods. Additionally, the order in which a particular method occurs mayor may not strictly adhere to the order of the corresponding stepsshown.

FIG. 6 is a block diagram illustrating an apparatus 600 according tovarious embodiments of the present disclosure. As shown in FIG. 6, theapparatus 600 may comprise one or more processors such as processor 601and one or more memories such as memory 602 storing computer programcodes 603. The memory 602 may be non-transitorymachine/processor/computer readable storage medium. In accordance withsome exemplary embodiments, the apparatus 600 may be implemented as anintegrated circuit chip or module that can be plugged or installed intoa terminal device as described with respect to FIG. 3, or a network nodeas described with respect to FIG. 5.

In some implementations, the one or more memories 602 and the computerprogram codes 603 may be configured to, with the one or more processors601, cause the apparatus 600 at least to perform any operation of themethod as described in connection with FIG. 3. In other implementations,the one or more memories 602 and the computer program codes 603 may beconfigured to, with the one or more processors 601, cause the apparatus600 at least to perform any operation of the method as described inconnection with FIG. 5.

Alternatively or additionally, the one or more memories 602 and thecomputer program codes 603 may be configured to, with the one or moreprocessors 601, cause the apparatus 600 at least to perform more or lessoperations to implement the proposed methods according to the exemplaryembodiments of the present disclosure.

FIG. 7 is a block diagram illustrating an apparatus 700 according tosome embodiments of the present disclosure. As shown in FIG. 7, theapparatus 700 may comprise a receiving unit 701 and a determining unit702. In an exemplary embodiment, the apparatus 700 may be implemented ina terminal device such as a UE. The receiving unit 701 may be operableto carry out the operation in block 302, and the determining unit 702may be operable to carry out the operation in block 304. Optionally, thereceiving unit 701 and/or the determining unit 702 may be operable tocarry out more or less operations to implement the proposed methodsaccording to the exemplary embodiments of the present disclosure.

FIG. 8 is a block diagram illustrating an apparatus 800 according tosome embodiments of the present disclosure. As shown in FIG. 8, theapparatus 800 may comprise a determining unit 801 and a transmittingunit 802. In an exemplary embodiment, the apparatus 800 may beimplemented in a network node such as a gNB. The determining unit 801may be operable to carry out the operation in block 502, and thetransmitting unit 802 may be operable to carry out the operation inblock 504. Optionally, the determining unit 801 and/or the transmittingunit 802 may be operable to carry out more or less operations toimplement the proposed methods according to the exemplary embodiments ofthe present disclosure.

In an embodiment, there is provided a method implemented at a terminaldevice. The method comprises receiving from a network node indicationinformation of time domain resource allocation for a non-remainingminimum system information, non-RMSI, message; and determining alocation of time domain resource for the non-RMSI message based at leastin part on the indication information. The indication information isfrom a physical downlink shared channel, PDSCH, time domain resourceallocation table specified for a remaining minimum system information,RMSI, message. The PDSCH time domain resource allocation table isassociated with synchronization signal/physical broadcast channel,SS/PBCH, block and control resource set, CORESET, multiplexing types 2and 3, and the indication information is received as a part of downlinkcontrol information carried by a channel in a control resource set.

In an embodiment, the PDSCH time domain resource allocation table may beadded one or more entries.

In an embodiment, the PDSCH time domain resource allocation tablecomprises at least one of the following parameters: physical downlinkshared channel, PDSCH, mapping type, slot level offset, start symbolindex and an allocated number of orthogonal frequency divisionmultiplexing, OFDM, symbols, wherein the PDSCH mapping type comprisesType A and/or Type B, and/or the slot level offset comprises 0, 1 and/orinteger greater than 1, and/or the start symbol index comprises at leastone of the 0, 1, 2, 3, 4, 6, 8, 9, 10, 11, 12, and/or the allocatednumber of OFDM symbol comprises at least one of 2, 4, 7, and integergreater than 7.

In an embodiment, the non-RMSI message comprises at least one of apaging message, random access response, RAR, message, Msg4 of randomaccess procedure, and other system information, OSI, and a unicastmessage.

In an embodiment, there is provided an apparatus implemented in aterminal device. The apparatus comprises one or more processors; and oneor more memories comprising computer program codes, the one or morememories and the computer program codes configured to, with the one ormore processors, cause the apparatus at least to receive from a networknode indication information of time domain resource allocation for anon-remaining minimum system information, non-RMSI, message; anddetermine a location of time domain resource for the non-RMSI messagebased at least in part on the indication information. The indicationinformation is from a physical downlink shared channel, PDSCH, timedomain resource allocation table specified for a remaining minimumsystem information, RMSI, message. The PDSCH time domain resourceallocation table is associated with synchronization signal/physicalbroadcast channel, SS/PBCH, block and control resource set, CORESET,multiplexing types 2 and 3, and the indication information is receivedas a part of downlink control information carried by a channel in acontrol resource set.

In an embodiment, there is provided a method implemented at a networknode. The method comprises determining indication information of timedomain resource allocation for a non-remaining minimum systeminformation, non-RMSI, message; and transmitting the indicationinformation to the terminal device. A location of time domain resourcefor the non-RMSI message is determined based at least in part on theindication information. The indication information is from a physicaldownlink shared channel, PDSCH, time domain resource allocation tablespecified for a remaining minimum system information, RMSI, message. ThePDSCH time domain resource allocation table is associated withsynchronization signal/physical broadcast channel, SS/PBCH, block andcontrol resource set, CORESET, multiplexing types 2 and 3, and theindication information is transmitted as a part of downlink controlinformation carried by a channel in a control resource set.

In an embodiment, the PDSCH time domain resource allocation table isadded one or more entries.

In an embodiment, the PDSCH time domain resource allocation tablecomprises at least one of the following parameters: physical downlinkshared channel, PDSCH, mapping type, slot level offset, start symbolindex and an allocated number of orthogonal frequency divisionmultiplexing, OFDM, symbols, wherein the PDSCH mapping type comprisesType A and/or Type B, and/or the slot level offset comprises 0, 1 and/orinteger greater than 1, and/or the start symbol index comprises at leastone of the 0, 1, 2, 3, 4, 6, 8, 9, 10, 11, 12, and/or the allocatednumber of OFDM symbol comprises at least one of 2, 4, 7, and integergreater than 7.

In an embodiment, the non-RMSI message comprises at least one of apaging message, random access response, RAR, message, Msg4 of randomaccess procedure, and other system information, OSI, and a unicastmessage.

In an embodiment, there is provided an apparatus implemented in anetwork node. The apparatus comprises one or more processors; and one ormore memories comprising computer program codes, the one or morememories and the computer program codes configured to, with the one ormore processors, cause the apparatus at least to determine indicationinformation of time domain resource allocation for a non-remainingminimum system information, non-RMSI, message; and transmit theindication information to the terminal device. A location of time domainresource for the non-RMSI message is determined based at least in parton the indication information. The indication information is from aphysical downlink shared channel, PDSCH, time domain resource allocationtable specified for a remaining minimum system information, RMSI,message. The PDSCH time domain resource allocation table is associatedwith synchronization signal/physical broadcast channel, SS/PBCH, blockand control resource set, CORESET, multiplexing types 2 and 3, and theindication information is transmitted as a part of downlink controlinformation carried by a channel in a control resource set.

In an embodiment, there is provided a computer-readable medium havingcomputer program codes embodied thereon for use with a computer, whereinthe computer program codes comprise codes for performing the methodrelated to the terminal device as described above.

In an embodiment, there is provided a computer-readable medium havingcomputer program codes embodied thereon for use with a computer, whereinthe computer program codes comprise codes for performing the methodrelated to the network device as described above.

In an embodiment, there is provided an apparatus implemented in aterminal device. The apparatus comprises a receiving unit configured toreceive from a network node indication information of time domainresource allocation for a non-remaining minimum system information,non-RMSI, message; and a determining unit configured to determine alocation of time domain resource for the non-RMSI message based at leastin part on the indication information. The indication information isfrom a physical downlink shared channel, PDSCH, time domain resourceallocation table specified for a remaining minimum system information,RMSI, message. The PDSCH time domain resource allocation table isassociated with synchronization signal/physical broadcast channel,SS/PBCH, block and control resource set, CORESET, multiplexing types 2and 3, and the indication information is received as a part of downlinkcontrol information carried by a channel in a control resource set.

In an embodiment, there is provided an apparatus implemented in anetwork node. The apparatus comprises a determining unit configured todetermine indication information of time domain resource allocation fora non-remaining minimum system information, non-RMSI, message; and atransmitting unit configured to transmit the indication information tothe terminal device. A location of time domain resource for the non-RMSImessage is determined based at least in part on the indicationinformation. The indication information is from a physical downlinkshared channel, PDSCH, time domain resource allocation table specifiedfor a remaining minimum system information, RMSI, message. The PDSCHtime domain resource allocation table is associated with synchronizationsignal/physical broadcast channel, SS/PBCH, block and control resourceset, CORESET, multiplexing types 2 and 3, and the indication informationis transmitted as a part of downlink control information carried by achannel in a control resource set.

FIG. 9 is a block diagram illustrating a telecommunication networkconnected via an intermediate network to a host computer in accordancewith some embodiments of the present disclosure.

With reference to FIG. 9, in accordance with an embodiment, acommunication system includes a telecommunication network 910, such as a3GPP-type cellular network, which comprises an access network 911, suchas a radio access network, and a core network 914. The access network911 comprises a plurality of base stations 912 a, 912 b, 912 c, such asNBs, eNBs, gNBs or other types of wireless access points, each defininga corresponding coverage area 913 a, 913 b, 913 c. Each base station 912a, 912 b, 912 c is connectable to the core network 914 over a wired orwireless connection 915. A first UE 991 located in a coverage area 913 cis configured to wirelessly connect to, or be paged by, thecorresponding base station 912 c. A second UE 992 in a coverage area 913a is wirelessly connectable to the corresponding base station 912 a.While a plurality of UEs 991, 992 are illustrated in this example, thedisclosed embodiments are equally applicable to a situation where a soleUE is in the coverage area or where a sole UE is connecting to thecorresponding base station 912.

The telecommunication network 910 is itself connected to a host computer930, which may be embodied in the hardware and/or software of astandalone server, a cloud-implemented server, a distributed server oras processing resources in a server farm. The host computer 930 may beunder the ownership or control of a service provider, or may be operatedby the service provider or on behalf of the service provider.Connections 921 and 922 between the telecommunication network 910 andthe host computer 930 may extend directly from the core network 914 tothe host computer 930 or may go via an optional intermediate network920. An intermediate network 920 may be one of, or a combination of morethan one of, a public, private or hosted network; the intermediatenetwork 920, if any, may be a backbone network or the Internet; inparticular, the intermediate network 920 may comprise two or moresub-networks (not shown).

The communication system of FIG. 9 as a whole enables connectivitybetween the connected UEs 991, 992 and the host computer 930. Theconnectivity may be described as an over-the-top (OTT) connection 950.The host computer 930 and the connected UEs 991, 992 are configured tocommunicate data and/or signaling via the OTT connection 950, using theaccess network 911, the core network 914, any intermediate network 920and possible further infrastructure (not shown) as intermediaries. TheOTT connection 950 may be transparent in the sense that theparticipating communication devices through which the OTT connection 950passes are unaware of routing of uplink and downlink communications. Forexample, the base station 912 may not or need not be informed about thepast routing of an incoming downlink communication with data originatingfrom the host computer 930 to be forwarded (e.g., handed over) to aconnected UE 991. Similarly, the base station 912 need not be aware ofthe future routing of an outgoing uplink communication originating fromthe UE 991 towards the host computer 930.

FIG. 10 is a block diagram illustrating a host computer communicatingvia a base station with a UE over a partially wireless connection inaccordance with some embodiments of the present disclosure.

Example implementations, in accordance with an embodiment, of the UE,base station and host computer discussed in the preceding paragraphswill now be described with reference to FIG. 10. In a communicationsystem 1000, a host computer 1010 comprises hardware 1015 including acommunication interface 1016 configured to set up and maintain a wiredor wireless connection with an interface of a different communicationdevice of the communication system 1000. The host computer 1010 furthercomprises a processing circuitry 1018, which may have storage and/orprocessing capabilities. In particular, the processing circuitry 1018may comprise one or more programmable processors, application-specificintegrated circuits, field programmable gate arrays or combinations ofthese (not shown) adapted to execute instructions. The host computer1010 further comprises software 1011, which is stored in or accessibleby the host computer 1010 and executable by the processing circuitry1018. The software 1011 includes a host application 1012. The hostapplication 1012 may be operable to provide a service to a remote user,such as UE 1030 connecting via an OTT connection 1050 terminating at theUE 1030 and the host computer 1010. In providing the service to theremote user, the host application 1012 may provide user data which istransmitted using the OTT connection 1050.

The communication system 1000 further includes a base station 1020provided in a telecommunication system and comprising hardware 1025enabling it to communicate with the host computer 1010 and with the UE1030. The hardware 1025 may include a communication interface 1026 forsetting up and maintaining a wired or wireless connection with aninterface of a different communication device of the communicationsystem 1000, as well as a radio interface 1027 for setting up andmaintaining at least a wireless connection 1070 with the UE 1030 locatedin a coverage area (not shown in FIG. 10) served by the base station1020. The communication interface 1026 may be configured to facilitate aconnection 1060 to the host computer 1010. The connection 1060 may bedirect or it may pass through a core network (not shown in FIG. 10) ofthe telecommunication system and/or through one or more intermediatenetworks outside the telecommunication system. In the embodiment shown,the hardware 1025 of the base station 1020 further includes a processingcircuitry 1028, which may comprise one or more programmable processors,application-specific integrated circuits, field programmable gate arraysor combinations of these (not shown) adapted to execute instructions.The base station 1020 further has software 1021 stored internally oraccessible via an external connection.

The communication system 1000 further includes the UE 1030 alreadyreferred to. Its hardware 1035 may include a radio interface 1037configured to set up and maintain a wireless connection 1070 with a basestation serving a coverage area in which the UE 1030 is currentlylocated. The hardware 1035 of the UE 1030 further includes a processingcircuitry 1038, which may comprise one or more programmable processors,application-specific integrated circuits, field programmable gate arraysor combinations of these (not shown) adapted to execute instructions.The UE 1030 further comprises software 1031, which is stored in oraccessible by the UE 1030 and executable by the processing circuitry1038. The software 1031 includes a client application 1032. The clientapplication 1032 may be operable to provide a service to a human ornon-human user via the UE 1030, with the support of the host computer1010. In the host computer 1010, an executing host application 1012 maycommunicate with the executing client application 1032 via the OTTconnection 1050 terminating at the UE 1030 and the host computer 1010.In providing the service to the user, the client application 1032 mayreceive request data from the host application 1012 and provide userdata in response to the request data. The OTT connection 1050 maytransfer both the request data and the user data. The client application1032 may interact with the user to generate the user data that itprovides.

It is noted that the host computer 1010, the base station 1020 and theUE 1030 illustrated in FIG. 10 may be similar or identical to the hostcomputer 930, one of base stations 912 a, 912 b, 912 c and one of UEs991, 992 of FIG. 9, respectively. This is to say, the inner workings ofthese entities may be as shown in FIG. 10 and independently, thesurrounding network topology may be that of FIG. 9.

In FIG. 10, the OTT connection 1050 has been drawn abstractly toillustrate the communication between the host computer 1010 and the UE1030 via the base station 1020, without explicit reference to anyintermediary devices and the precise routing of messages via thesedevices. Network infrastructure may determine the routing, which it maybe configured to hide from the UE 1030 or from the service provideroperating the host computer 1010, or both. While the OTT connection 1050is active, the network infrastructure may further take decisions bywhich it dynamically changes the routing (e.g., on the basis of loadbalancing consideration or reconfiguration of the network).

Wireless connection 1070 between the UE 1030 and the base station 1020is in accordance with the teachings of the embodiments describedthroughout this disclosure. One or more of the various embodimentsimprove the performance of OTT services provided to the UE 1030 usingthe OTT connection 1050, in which the wireless connection 1070 forms thelast segment. More precisely, the teachings of these embodiments mayimprove the latency and the power consumption, and thereby providebenefits such as lower complexity, reduced time required to access acell, better responsiveness, extended battery lifetime, etc.

A measurement procedure may be provided for the purpose of monitoringdata rate, latency and other factors on which the one or moreembodiments improve. There may further be an optional networkfunctionality for reconfiguring the OTT connection 1050 between the hostcomputer 1010 and the UE 1030, in response to variations in themeasurement results. The measurement procedure and/or the networkfunctionality for reconfiguring the OTT connection 1050 may beimplemented in software 1011 and hardware 1015 of the host computer 1010or in software 1031 and hardware 1035 of the UE 1030, or both. Inembodiments, sensors (not shown) may be deployed in or in associationwith communication devices through which the OTT connection 1050 passes;the sensors may participate in the measurement procedure by supplyingvalues of the monitored quantities exemplified above, or supplyingvalues of other physical quantities from which the software 1011, 1031may compute or estimate the monitored quantities. The reconfiguring ofthe OTT connection 1050 may include message format, retransmissionsettings, preferred routing etc.; the reconfiguring need not affect thebase station 1020, and it may be unknown or imperceptible to the basestation 1020. Such procedures and functionalities may be known andpracticed in the art. In certain embodiments, measurements may involveproprietary UE signaling facilitating the host computer 1010'smeasurements of throughput, propagation times, latency and the like. Themeasurements may be implemented in that the software 1011 and 1031causes messages to be transmitted, in particular empty or ‘dummy’messages, using the OTT connection 1050 while it monitors propagationtimes, errors etc.

FIG. 11 is a flowchart illustrating a method implemented in acommunication system, in accordance with an embodiment. Thecommunication system includes a host computer, a base station and a UEwhich may be those described with reference to FIG. 9 and FIG. 10. Forsimplicity of the present disclosure, only drawing references to FIG. 11will be included in this section. In step 1110, the host computerprovides user data. In substep 1111 (which may be optional) of step1110, the host computer provides the user data by executing a hostapplication. In step 1120, the host computer initiates a transmissioncarrying the user data to the UE. In step 1130 (which may be optional),the base station transmits to the UE the user data which was carried inthe transmission that the host computer initiated, in accordance withthe teachings of the embodiments described throughout this disclosure.In step 1140 (which may also be optional), the UE executes a clientapplication associated with the host application executed by the hostcomputer.

FIG. 12 is a flowchart illustrating a method implemented in acommunication system, in accordance with an embodiment. Thecommunication system includes a host computer, a base station and a UEwhich may be those described with reference to FIG. 9 and FIG. 10. Forsimplicity of the present disclosure, only drawing references to FIG. 12will be included in this section. In step 1210 of the method, the hostcomputer provides user data. In an optional substep (not shown) the hostcomputer provides the user data by executing a host application. In step1220, the host computer initiates a transmission carrying the user datato the UE. The transmission may pass via the base station, in accordancewith the teachings of the embodiments described throughout thisdisclosure. In step 1230 (which may be optional), the UE receives theuser data carried in the transmission.

FIG. 13 is a flowchart illustrating a method implemented in acommunication system, in accordance with an embodiment. Thecommunication system includes a host computer, a base station and a UEwhich may be those described with reference to FIG. 9 and FIG. 10. Forsimplicity of the present disclosure, only drawing references to FIG. 13will be included in this section. In step 1310 (which may be optional),the UE receives input data provided by the host computer. Additionallyor alternatively, in step 1320, the UE provides user data. In substep1321 (which may be optional) of step 1320, the UE provides the user databy executing a client application. In substep 1311 (which may beoptional) of step 1310, the UE executes a client application whichprovides the user data in reaction to the received input data providedby the host computer. In providing the user data, the executed clientapplication may further consider user input received from the user.Regardless of the specific manner in which the user data was provided,the UE initiates, in substep 1330 (which may be optional), transmissionof the user data to the host computer. In step 1340 of the method, thehost computer receives the user data transmitted from the UE, inaccordance with the teachings of the embodiments described throughoutthis disclosure.

FIG. 14 is a flowchart illustrating a method implemented in acommunication system, in accordance with an embodiment. Thecommunication system includes a host computer, a base station and a UEwhich may be those described with reference to FIG. 9 and FIG. 10. Forsimplicity of the present disclosure, only drawing references to FIG. 14will be included in this section. In step 1410 (which may be optional),in accordance with the teachings of the embodiments described throughoutthis disclosure, the base station receives user data from the UE. Instep 1420 (which may be optional), the base station initiatestransmission of the received user data to the host computer. In step1430 (which may be optional), the host computer receives the user datacarried in the transmission initiated by the base station.

In general, the various exemplary embodiments may be implemented inhardware or special purpose chips, circuits, software, logic or anycombination thereof. For example, some aspects may be implemented inhardware, while other aspects may be implemented in firmware or softwarewhich may be executed by a controller, microprocessor or other computingdevice, although the disclosure is not limited thereto. While variousaspects of the exemplary embodiments of this disclosure may beillustrated and described as block diagrams, flow charts, or using someother pictorial representation, it is well understood that these blocks,apparatus, systems, techniques or methods described herein may beimplemented in, as non-limiting examples, hardware, software, firmware,special purpose circuits or logic, general purpose hardware orcontroller or other computing devices, or some combination thereof.

As such, it should be appreciated that at least some aspects of theexemplary embodiments of the disclosure may be practiced in variouscomponents such as integrated circuit chips and modules. It should thusbe appreciated that the exemplary embodiments of this disclosure may berealized in an apparatus that is embodied as an integrated circuit,where the integrated circuit may comprise circuitry (as well as possiblyfirmware) for embodying at least one or more of a data processor, adigital signal processor, baseband circuitry and radio frequencycircuitry that are configurable so as to operate in accordance with theexemplary embodiments of this disclosure.

It should be appreciated that at least some aspects of the exemplaryembodiments of the disclosure may be embodied in computer-executableinstructions, such as in one or more program modules, executed by one ormore computers or other devices. Generally, program modules includeroutines, programs, objects, components, data structures, etc. thatperform particular tasks or implement particular abstract data typeswhen executed by a processor in a computer or other device. The computerexecutable instructions may be stored on a computer readable medium suchas a hard disk, optical disk, removable storage media, solid statememory, random access memory (RAM), etc. As will be appreciated by oneof skill in the art, the function of the program modules may be combinedor distributed as desired in various embodiments. In addition, thefunction may be embodied in whole or partly in firmware or hardwareequivalents such as integrated circuits, field programmable gate arrays(FPGA), and the like.

The present disclosure includes any novel feature or combination offeatures disclosed herein either explicitly or any generalizationthereof. Various modifications and adaptations to the foregoingexemplary embodiments of this disclosure may become apparent to thoseskilled in the relevant arts in view of the foregoing description, whenread in conjunction with the accompanying drawings. However, any and allmodifications will still fall within the scope of the non-limiting andexemplary embodiments of this disclosure.

1.-30. (canceled)
 31. A method implemented at a terminal device,comprising: receiving from a network node indication information of timedomain resource allocation for a non-remaining minimum systeminformation, non-RMSI, message; and determining a location of timedomain resource for the non-RMSI message based at least in part on theindication information, wherein the indication information is from aphysical downlink shared channel, PDSCH, time domain resource allocationtable specified for a remaining minimum system information, RMSI,message; wherein the PDSCH time domain resource allocation table isassociated with synchronization signal/physical broadcast channel,SS/PBCH, block and control resource set, CORESET, multiplexing types 2and 3, and the indication information is received as a part of downlinkcontrol information carried by a channel in a control resource set. 32.The method according to claim 31, wherein the PDSCH time domain resourceallocation table is added one or more entries.
 33. The method accordingto claim 31, wherein the PDSCH time domain resource allocation tablecomprises at least one of the following parameters: physical downlinkshared channel, PDSCH, mapping type, slot level offset, start symbolindex and an allocated number of orthogonal frequency divisionmultiplexing, OFDM, symbols, wherein the PDSCH mapping type comprisesType A and/or Type B, and/or the slot level offset comprises 0, 1 and/orinteger greater than 1, and/or the start symbol index comprises at leastone of the 0, 1, 2, 3, 4, 6, 8, 9, 10, 11, 12, and/or the allocatednumber of OFDM symbol comprises at least one of 2, 4, 7, and integergreater than
 7. 34. The method according to claim 31 wherein thenon-RMSI message comprises at least one of a paging message, randomaccess response, RAR, message, Msg4 of random access procedure, andother system information, OSI, and a unicast message.
 35. An apparatusimplemented in a terminal device, comprising: one or more processors;and one or more memories comprising computer program codes, the one ormore memories and the computer program codes configured to, with the oneor more processors, cause the apparatus at least to: receive from anetwork node indication information of time domain resource allocationfor a non-remaining minimum system information, non-RMSI, message; anddetermine a location of time domain resource for the non-RMSI messagebased at least in part on the indication information, wherein theindication information is from a physical downlink shared channel,PDSCH, time domain resource allocation table specified for a remainingminimum system information, RMSI, message; wherein the PDSCH time domainresource allocation table is associated with synchronizationsignal/physical broadcast channel, SS/PBCH, block and control resourceset, CORESET, multiplexing types 2 and 3, and the indication informationis received as a part of downlink control information carried by achannel in a control resource set.
 36. (canceled)
 37. A methodimplemented at a network node, comprising: determining indicationinformation of time domain resource allocation for a non-remainingminimum system information, non-RMSI, message; and transmitting theindication information to the terminal device, wherein a location oftime domain resource for the non-RMSI message is determined based atleast in part on the indication information, wherein the indicationinformation is from a physical downlink shared channel, PDSCH, timedomain resource allocation table specified for a remaining minimumsystem information, RMSI, message; wherein the PDSCH time domainresource allocation table is associated with synchronizationsignal/physical broadcast channel, SS/PBCH, block and control resourceset, CORESET, multiplexing types 2 and 3, and the indication informationis transmitted as a part of downlink control information carried by achannel in a control resource set.
 38. The method according to claim 37,wherein the PDSCH time domain resource allocation table is added one ormore entries.
 39. The method according to claim 37, wherein the PDSCHtime domain resource allocation table comprises at least one of thefollowing parameters: physical downlink shared channel, PDSCH, mappingtype, slot level offset, start symbol index and an allocated number oforthogonal frequency division multiplexing, OFDM, symbols, wherein thePDSCH mapping type comprises Type A and/or Type B, and/or the slot leveloffset comprises 0, 1 and/or integer greater than 1, and/or the startsymbol index comprises at least one of the 0, 1, 2, 3, 4, 6, 8, 9, 10,11, 12, and/or the allocated number of OFDM symbol comprises at leastone of 2, 4, 7, and integer greater than
 7. 40. The method according toclaim 37, wherein the non-RMSI message comprises at least one of apaging message, random access response, RAR, message, Msg4 of randomaccess procedure, and other system information, OSI, and a unicastmessage. 41.-46. (canceled)
 47. The apparatus according to claim 35,wherein the PDSCH time domain resource allocation table is added one ormore entries.
 48. The apparatus according to claim 35, wherein the PDSCHtime domain resource allocation table comprises at least one of thefollowing parameters: physical downlink shared channel, PDSCH, mappingtype, slot level offset, start symbol index and an allocated number oforthogonal frequency division multiplexing, OFDM, symbols, wherein thePDSCH mapping type comprises Type A and/or Type B, and/or the slot leveloffset comprises 0, 1 and/or integer greater than 1, and/or the startsymbol index comprises at least one of the 0, 1, 2, 3, 4, 6, 8, 9, 10,11, 12, and/or the allocated number of OFDM symbol comprises at leastone of 2, 4, 7, and integer greater than
 7. 49. The apparatus accordingto claim 35, wherein the non-RMSI message comprises at least one of apaging message, random access response, RAR, message, Msg4 of randomaccess procedure, and other system information, OSI, and a unicastmessage.